-
Notifications
You must be signed in to change notification settings - Fork 883
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perform download safety check even when user is prompted for save location. #16969
Conversation
c2d26ae
to
19a22e9
Compare
|
19a22e9
to
b54d9d2
Compare
Verification PASSED on
Using the STR/Cases outlined via brave/brave-browser#28079 (comment), went through the following:
|
Example |
Example |
Example |
Example |
Example |
---|---|---|---|---|
Test Case #2
- Brave Custom (Ask where to save each file before downloading
disabled)
- disable
Ask where to save each file before downloading
viabrave://settings/downloads
- ensured that the
This type of file can harm your computer
error appeared at the bottom of the window- ensured that selecting
Keep
saved the@aexample.scf
into the correct location - ensured that selecting
Discard
removes the file and doesn't save it (removes entry frombrave://downloads
as well) - ensured that clicking on
Show all
opensbrave://downloads
and lists the current entry with the warning
- ensured that selecting
- ensured the entry within
brave://downloads
has the option toDiscard
orKeep
the file- ensured that selecting
Discard
removes the file and doesn't save it (removes entry frombrave://downloads
as well) - ensured that selecting
Keep
displayed a modal confirmation about saving the file locally- ensured that selecting
Cancel
returns the user back tobrave://downloads
but doesn't remove the file/decision - ensured that selecting
Keep
downloads the@aexample.scf
file locally without any issues
- ensured that selecting
- ensured that the
@aexample.scf
entry appears withinbrave://downloads
ifKeep
was selected
- ensured that selecting
Example |
Example |
Example |
---|---|---|
Test Case #3
- Installing Packed Extension
Using the STR/Cases outlined via brave/brave-browser#28079 (comment), packed the 1Password
extension and ensured that it installed without any warnings re: the files not being safe as per the following:
Example |
Example |
Example |
Example |
---|---|---|---|
* License, v. 2.0. If a copy of the MPL was not distributed with this file, | ||
* You can obtain one at https://mozilla.org/MPL/2.0/. */ | ||
|
||
// Prompting the user for download location shouldn't be a factor in determining |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused because this looks like an upstream issue if there is an issue here, but the location does affect the danger level which is why macOS prompts for permission to access different file system locations for each app
Resolves brave/brave-browser#28079
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
wikinpm run lint
,npm run presubmit
wiki,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan: